Update all dependencies - #1147

v7.1.1

Compare Source

What's Changed

• chore(release): 7.1.1 by @​thomasrockhu-codecov in #​1973

Full Changelog: codecov/codecov-action@v7.1.0...v7.1.1

v7.1.0

Compare Source

What's Changed

• chore(release): 7.1.0 by @​thomasrockhu-codecov in #​1971

Full Changelog: codecov/codecov-action@v7.0.0...v7.1.0

v4.39.0

Compare Source

• Breaking change: Bump the minimum required CodeQL bundle version to 2.20.7. #​4205
• The codeql-action/analyze step now validates that a correct argument for the checkout_path input has been provided. The checkout_path input must be set to the path where the repository that is being analyzed is checked out at on the runner, if that path is something other than the workspace root. If the path does not point to a repository checkout or is different from the path that was used by codeql-action/init, then the CodeQL Action now produces a warning. #​4148
• Resolved an issue with third-party caching implementations that prevented caches from being restored correctly. #​4206
• The codeql-action/start-proxy step that is used in Code Scanning Default Setup now finds CodeQL releases using the same logic as codeql-action/init. This primarily benefits customers who are using GitHub instances other than github.com where the codeql-action/start-proxy step may previously have been unable to locate recent releases and ended up using outdated versions of the private registry authentication proxy as a result. #​4198

v4.38.3

Compare Source

• Upcoming breaking change: CodeQL version 2.21.2 and earlier were discontinued on 24 September 2026 alongside GitHub Enterprise Server 3.17, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #​4188
• Update default CodeQL bundle version to 2.27.2. #​4203
• Fixed a bug where the decision of whether to use a per-language bundle did not account for custom configurations that reference queries outside of compiled CodeQL packs. This issue was caught during internal testing and did not affect any customer repositories. We will resume the roll out of per-language bundles in the coming weeks. #​4184

v4.38.2

Compare Source

• Update default CodeQL bundle version to 2.27.1. #​4160

v4.38.1

Compare Source

• The CodeQL Action now has experimental support for CodeQL releases for which per-language bundles are available. Per-language bundles support analysis for a single language and are therefore smaller than the combined bundles that allow analysis for all supported languages. As a result, per-language bundles take up less space on disk and are faster to download. We expect to roll this change out to everyone in the coming weeks. #​4146

v4.38.0

Compare Source

• On GitHub-hosted runners, the CodeQL Action now deletes unused CodeQL bundles from the toolcache before downloading a different bundle, which frees up disk space for the analysis. We expect to roll this change out to everyone in September. #​4124
• The CodeQL Action now supports CodeQL releases that are compatible with Linux Arm64 and downloads the native linux-arm64 CodeQL bundle when available. #​4072
• Update default CodeQL bundle version to 2.27.0. #​4129

v4.37.9

Compare Source

• Update default CodeQL bundle version to 2.26.4. #​4106

v9.8.1: 9.8.1

Compare Source

This is a patch release for Gradle 9.8.0. We recommend using 9.8.1 instead of 9.8.0.

This release addresses three high rated vulnerabilities:

• Unauthenticated worker-to-daemon channel deserializes untrusted Java objects
• Deserialization of untrusted Java objects before authentication in the client - daemon communication
• Failure to disable repositories failing to establish an SSL connection can expose builds to malicious artifacts

The following issues were resolved:

• [Gradle 9.8.0 complains again about invalid Toolchains on Debian / Ubuntu packaged systems]- (#​39358)
• Gradle 9.8.0 removes root java.util.logging handlers installed by a custom LogManager (breaks Quarkus test log capture)
• Dependency resolution regression

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Aman Gautam,
Björn Kautler,
Eng Zer Jun,
Hashim Khan,
Julian Krannich,
KBS,
Labh R Jethe,
Mark Dodgson,
Maxim,
monkey,
nataphon-ktsystems,
Paul King,
Qiu Tian,
rg_sandesh,
Roberto Perez Alcolea,
Sean,
Zongle Wang.

Upgrade instructions

Switch your build to use Gradle 9.8.1 by updating your wrapper:

./gradlew :wrapper --gradle-version=9.8.1 && ./gradlew :wrapper

See the Gradle 9.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v9.8.0: 9.8.0

Compare Source

The Gradle team is excited to announce Gradle 9.8.0.

Here are the highlights of this release:

• Java 27 support
• Maven mirror settings reuse
• Linked problem locations in build output

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Aman Gautam,
Björn Kautler,
Eng Zer Jun,
Hashim Khan,
Julian Krannich,
KBS,
Labh R Jethe,
Mark Dodgson,
Maxim,
monkey,
nataphon-ktsystems,
Paul King,
Qiu Tian,
rg_sandesh,
Roberto Perez Alcolea,
Sean,
Zongle Wang.

Upgrade instructions

Switch your build to use Gradle 9.8.0 by updating your wrapper:

./gradlew :wrapper --gradle-version=9.8.0 && ./gradlew :wrapper

See the Gradle 9.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v6.4.0

Compare Source

Highlights

Gradle version support status in the Job Summary

The actions now report the support status of every Gradle version used in a workflow, as job
annotations and in the Job Summary (#​1057). Thanks to @​ov7a for the contribution.

Deliberately not reported: patch releases (being on 9.7.0 when 9.7.1 exists is not flagged) and
pre-releases (release candidates, milestones and snapshots never produce annotations). The latest
Gradle release is determined from the wrapper checksum data already bundled with the action, so no
network access is required.

Note that these annotations are emitted independently of the add-job-summary setting: setting
add-job-summary: 'never' suppresses the Job Summary itself, but the warning and notice annotations
remain.

Gradle itself is now reported in the dependency graph

The dependency-submission action now applies v1.5.0 of the
GitHub Dependency Graph Gradle Plugin
(up from v1.4.2) (#​1069).

The headline change is that the Gradle Build Tool running the build is now reported as an
org.gradle:gradle-core dependency, so that GitHub can surface known vulnerabilities in the version
of Gradle used to run your build. These are the coordinates that GitHub advisories for the Gradle
Build Tool are published against.

Details worth knowing:

• The entry is always reported as a direct dependency with development scope.
• It is not affected by the project, configuration or scope filters, so it appears even in graphs
  that filter aggressively.
• Expect dependency graphs to gain this one new entry the first time a build runs after upgrading.

A new Gradle signing key, if you use dependency verification

[!IMPORTANT]
If your build has dependency verification
enabled, you must add a second trusted key before upgrading, or Dependency Graph generation will
fail signature verification.

github-dependency-graph-gradle-plugin 1.5.0 is signed with a new Gradle signing subkey, and the
key previously documented in our setup guide has been revoked upstream:

Because the Develocity Gradle plugin is still signed with the old key, you should trust both keys
rather than swapping one for the other — replacing the old key outright will break Develocity
injection. The documented snippet in
docs/setup-gradle.md
has been updated accordingly (#​1071):

<trusted-keys>
   <trusted-key id="7B79ADD11F8A779FE90FD3D0893A028475557671">
      <trusting group="com.gradle"/>
      <trusting group="org.gradle"/>
   </trusted-key>
   <trusted-key id="E2879931BCA1A42E55F2D64DD9B2DFBD9F3298BA">
      <trusting group="org.gradle"/>
   </trusted-key>
</trusted-keys>

cache-provider: external for externally managed Gradle User Home

Builds that save and restore Gradle User Home by some other mechanism (Develocity Artifact Cache, for
example) previously had to set cache-disabled: true, which was misleading: caching wasn't disabled,
it just wasn't managed by this action, and the Job Summary reported it as "Disabled".

cache-provider: external skips Gradle User Home restore/save exactly as cache-disabled does, but
reports a distinct External status in the Job Summary explaining that caching is handled by
another provider (#​1059).

- uses: gradle/actions/setup-gradle@v6
  with:
    cache-provider: 'external'

Develocity access keys containing OIDC tokens now work

Short-lived-token handling validated the server=key[;server=key]* access key format with a regex
whose key portion was too strict, so an access key holding an OIDC token value was rejected
outright. Worse, had it passed the regex, parsing split each entry on = and kept only the second
field — silently truncating any key containing = (as JWT padding does) and sending the mangled
key to the server. Both problems are fixed (#​1061).

Job Summary attribution

Job summaries produced by setup-gradle and dependency-submission now carry a top-level heading
naming the action, so the block stays attributable when another action's summary content lands in the
same job (#​1058).

Updated defaults

• GitHub Dependency Graph Gradle Plugin: 1.4.2 → 1.5.0
• 5 new known-good wrapper checksums for wrapper-validation (368 → 373 entries)

What's Changed

• Bump the github-actions group across 3 directories with 6 updates by @​dependabot[bot] in #​1039
• Bump the npm-dependencies group in /sources with 3 updates by @​dependabot[bot] in #​1038
• Add action heading to Gradle job summary by @​bigdaz in #​1058
• Add cache-provider: external to skip Gradle User Home caching by @​bigdaz in #​1059
• Relax Develocity access key format validation by @​bigdaz in #​1061
• Use the root-qualified :wrapper task by @​cobexer in #​1064
• Report EOL and maintenance status for Gradle versions by @​ov7a in #​1057
• Update dependencies by @​bigdaz in #​1065
• Update .tool-versions: node 24.18.0, gradle 9.7.1, java 17 by @​bigdaz in #​1068
• Combined automated updates: wrapper checksums, npm dependencies, setup-java by @​bigdaz in #​1070
• Bump dependency-graph-gradle-plugin to 1.5.0 by @​bigdaz in #​1069
• Document the new Gradle signing key for dependency verification by @​bigdaz in #​1071

New Contributors

• @​cobexer made their first contribution in #​1064
• @​ov7a made their first contribution in #​1057

Full Changelog: gradle/actions@v6.3.0...v6.4.0

v17.6.0

Compare Source

Minor Changes

• #​1850 938d3f4 - Task functions like { title, task } can now use a logger function log() to emit output while the task runs. By default, the output will only be visible if the task fails, unless the --verbose option was used. Additionally, when the task rejects, the error will be shown in the output.

  import { defineConfig } from 'lint-staged/config'
  
  export default defineConfig({
    '*': {
      title: 'Fail if PDF files are committed',
      task: async (filepaths, { log }) => {
        const pdfFiles = filepaths.filter((f) => f.toLowerCase().endsWith('.pdf'))
        if (pdfFiles.length > 0) {
          log('PDF files should not be committed: %s', pdfFiles)
          throw new Error('Failed')
        }
      },
    },
  })

• #​1854 30562bc - lint-staged now stages changes to all tracked files modified by tasks, including files that weren’t originally staged or didn’t match the configured globs. This can happen when your task has side-effects, or it's a function that ignores the staged files like () => "prettier --write .".

  If you have unstaged changes in a file and the task also edits that file, your unstaged changes will be staged too. Use --hide-unstaged to hide your changes while tasks run.

Patch Changes

• #​1860 4296532 - The assignment of staged files to lint-staged configuration files (when using multiple, for example in a monorepo) has been rewritten to be more efficient. As a reminder, each staged file is assigned to exactly one configuration (the closest one), even if that config doesn't match the file in its globs.

• #​1861 c45f28a - Fix running parallel tasks for a single glob, when tasks are created by a function. Nesting one level of arrays inside an array of tasks will result in the inner tasks running in parallel. This behavior should now be consistent when creating tasks using functions. In the following example eslint and prettier will run in parallel (for all files, when any JS files are staged):

  import { defineConfig } from 'lint-staged/config'
  
  export default defineConfig({
    '*.js': () => [['eslint --max-warnings=0 .', 'prettier --list-different .']],
  })

• #​1859 f0ea69d - Various performance improvements from skipping redundant internal Git calls.

• #​1856 69d7d17 - Partially staged changes are hidden in a uniquely-named patch file to avoid multiple invocations of lint-staged overwriting it. This makes it safer to run lint-staged in multiple worktrees at the same time.

v17.5.1

Compare Source

Patch Changes

• #​1852 bfcca94 - Fix TypeScript issue TS1254 from defineConfig() by changing the signature from const to a function:

  A 'const' initializer in an ambient context must be a string or numeric literal or literal enum reference.

v17.5.0

Compare Source

Minor Changes

• #​1847 f9063b7 - Lint-staged now refuses to run when files were staged with --intent-to-add, because Git stash doesn't support them. Previously this was an unhandled error.

Patch Changes

• #​1848 d718ccc - Lint-staged now handles color support better in non-TTY streams, and honors the FORCE_COLOR environment variable.

• #​1845 7e5ece8 - Update tinyexec@1.3.1 so that local binaries from node_modules/.bin are resolved starting from the directory of each lint-staged configuration file (in monorepo setups). This behavior was broken in lint-staged@16.3.0 where they were only resolved from the current working directory and up.

• #​1845 eb8a4e3 - Do not try to restore untracked files when using --hide-all and there is no initial commit yet.

v17.4.1

Compare Source

Patch Changes

• #​1840 efe5b63 - This is a version-bump-only release because the previous version 17.4.0 was not published to npmjs.com due to problems with GitHub Actions and Changesets.

v8.7.0

What's Changed

• Strengthen lazy schema path test coverage (#​961) @​iuliiasobolevska, @​jiholee17

⭐ Improvements

• Support lazy file collections for GenerateJavaTask.schemaPaths (#​957) @​jiholee17

🔨 Dependency Upgrades

• Bump actions/checkout from 6 to 7 (#​946) @​dependabot[bot], @​iuliiasobolevska
• Bump actions/setup-python from 6.2.0 to 6.3.0 (#​948) @​dependabot[bot], @​iuliiasobolevska
• Bump actions/cache from 5 to 6 (#​949) @​dependabot[bot], @​iuliiasobolevska

v5.24.0

^{Changelog generated by Shipkit Changelog Gradle Plugin}

5.24.0

• 2026-09-23 - 27 commit(s) by Andrei Solntsev, DragonFSKY, Hünkar Can Tunç, Joshua Selbo, M. Minot, Markus Gaisbauer, Mirko Alicastro, Vinod Kumar M ( codingkiddo ), dependabot[bot]
• Fix Mockito docs for -javaagent flag with Gradle (#​3866)
• Kotlin example for adding Mockito as an agent is incorrect (#​3864)
• Bump graalvm/setup-graalvm from 1.6.3 to 1.6.6 (#​3862)
• Bump gradle/actions from 6.2.0 to 6.3.0 (#​3852)
• Bump gradle/actions from 5 to 6.2.0 (#​3851)
• Preserve method parameters when clearing inline mocks (#​3847)
• Bump graalvm/setup-graalvm from 1.6.0 to 1.6.3 (#​3845)
• Print object fields via reflection when toString() is not implemented (#​3844)
• Migrate extensions-tests to JUnit Jupiter (#​3840)
• Bump graalvm/setup-graalvm from 1.5.6 to 1.6.0 (#​3839)
• docs(when-verify): fixes to explanations about redundancy (#​3838)
• Confusing inconsistency in example method calls in “stubbing and verifying is redundant” note of “when” and “verify” Javadoc (#​3837)
• Bump actions/checkout from 6 to 7 (#​3836)
• Fixes #​2740 : Add mockMaker option to @Spy annotation (#​3835)
• Bump graalvm/setup-graalvm from 1.5.5 to 1.5.6 (#​3834)
• Bump graalvm/setup-graalvm from 1.5.4 to 1.5.5 (#​3833)
• Bump codecov/codecov-action from 6 to 7 (#​3831)
• Bump graalvm/setup-graalvm from 1.4.5 to 1.5.4 (#​3830)
• Fix clearInlineMocks not de-registering singleton mocks (#​3829)
• Fix NotAMockException when using mockSingleton with MockitoJUnit (#​3827)
• NotAMockException when using mockSingleton with MockitoSession or MockitoJUnit (#​3826)
• Improve Gradle agent docs for configuration cache (#​3823)
• Gradle documentation for setting up instrumentation with Gradle configuration cache (#​3822)
• Fixes #​3818 : Fix data race in InvocationContainerImpl.invocationForStubbing (#​3819)
• Data race on invocationForPotentialStubbing (#​3818)
• Fixes #​3814 : implement package-level clinit suppression (#​3815)
• Package-level clinit suppression (#​3814)
• Upgrade Android Gradle Plugin to 8.13.2 (#​3812)
• Replaces raw generic types with type parameters (#​3806)
• Fixes #​2398 : Implement global suppress static initialization leveraging java agent (#​3801)
• Bump codecov/codecov-action from 5 to 6 (#​3800)
• Fix non-deterministic AssertionError when using MockMakers.SUBCLASS (#​3406, #​2823) (#​3795)
• Fixes #​3536 : Implement SpyStatic API (#​3794)
• The class's MethodParameters are removed after clearAllCaches is invoked (#​3763)
• [FeatureRequest / Idea] Create Mockito.spyStatic (#​3536)
• Add option to specify mockmaker for @Spy (#​2740)
• How can I suppress static initializer? (#​2398)

v3.18.2

2026-09-04

• Fix: Don't change behavior of base64-encoding. We introduced a bug in Okio 3.18.1 that caused
  base64 strings to be encoded without padding, even though the previous and expected behavior is
  to encode such strings with padding (= characters). The bug impacts callers who compiled
  against Okio releases < 3.18.0, and executed on Okio releases >= 3.18.

v2.62.0

Added

• Clarify JavaScript source map listing and pagination #​4443
• Document public Deployment Gate and rule evaluation endpoints #​4442
• Add Heatgrid dashboard widget support #​4439
• Mark Bits Investigation endpoints as stable #​4438
• Add endpoint to override the severity of security findings #​4435
• Add reroute_to_team action to On-Call team routing rules #​4434
• Include the matched shard in the SPA v2 response #​4433
• Add aggregate event-time configuration to Observability Pipelines #​4427
• Publish Cloud Cost Management cloud account listing #​4426
• Add AI Impact user activity endpoint #​4418
• Rename Patch a deployment event to Mark a deployment as failed by ID #​4417
• Promote Mark a deployment as failed by version endpoint to GA #​4416
• Document Supply Chain Firewall reports API #​4415
• Add compatibleVersion to security monitoring rule responses #​4413
• Add CI job logs intake API #​4411
• Add Archive Search endpoints to the public API #​4409
• Add SPA recommendations v2 endpoint #​4408
• Add dashboard experience type to API responses #​4407
• Extend Cloud Auth Config endpoints to support new GitHub provider #​4406
• Add case_stream to dashboard list stream sources #​4401
• Add metrics enrichment table processor to Observability Pipelines #​4400
• Add bits_ai_auto_investigate to synthetics test options #​4397
• Document source field in DataDeletionResponseItemAttributes #​4396
• Document Flink as a Confluent Cloud resource type #​4392
• Document recently updated entities endpoint and entity_type parameter #​4391
• Publish stable Experiments v2 APIs #​4388
• Document leak information on personal and service access tokens #​4384
• Increase Reference Tables Upsert/DeleteRows payload limit to 1 MiB #​4372
• add recipient_email and servicenow to team notification rule #​4369
• Document the meta object returned by Reference Tables Get rows by id #​4352
• Add support for general investigations to Bits Investigations trigger API #​4345
• Document managed prompt message placeholders #​4317

Changed

• Document AI Impact user activity endpoint under DORA Metrics #​4437
• Document dashboard quality scores in usage APIs #​4424
• Update signalsDetected description to reflect risk-contributing signals #​4339

Fixed

• Allow null default_value in governance control parameter definitions #​4436
• Remove bearer token auth from the CreateEvent intake endpoint #​4432
• Clarify the Archive Search tag description #​4419
• Fix Workload Protection policy creation success response to 201 Created #​4412
• Document DDSQL query permissions and OAuth scope #​4390
• Specify UUID format for Databricks Private Action Runner connection fields #​4374
• CCM Recommendations API - Re-add filter request attribute and fix sort examples #​4358
• Automation pipelines require ID in updates and use different request/response schemas #​4290
• RUM Rename feature to journey strong link to link in comments and desc #​4262
• Document missing limitations and 409 response for org disable endpoint #​4108

Deprecated

• Deprecate Salesforce Incidents API endpoints #​4429

Removed

• Retire the RUM aggregated signals and problems endpoint #​4393

v2.61.0

Added

• Add bearer auth to endpoints that support api app key auth #​4362
• Document Deployment Gate evaluation APIs #​4361
• Update GCP V2 API spec to support is_org_folder_resource_collection_enabled #​4354
• allow billing read for ListQuotas GET endpoint #​4346
• Document run_as attribute and with_run_as param for downtime v2 API #​4340
• Add sensitivePrivileges field to Workflow Automation spec #​4334
• Add draft monitor permissions definition #​4333
• Document NDM device tag sources #​4325
• Document GetBudget response metadata #​4322
• LLMObs Document version-pinned prompt composition #​4316
• Add versioned prompt configuration #​4315
• Document OAuth v2 OIDC discovery endpoint #​4314
• Add prometheus remote write source and sink to obs-pipelines public api spec #​4310
• Allow up to three timeseries anomaly investigation results #​4309
• Security findings default and regular inbox rules API spec #​4307
• Add Integration Accounts v2 API for Snowflake #​4306
• Add downtime duration policy to Monitor Config Policy API spec [#​4304](https://redi

[!IMPORTANT]
✂ PR body was truncated to here.